🦋 Changeset detected

Latest commit: 5ef13fd

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/codemod@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server-legacy@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/express@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/fastify@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/hono@2163

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/node@2163

commit: 5ef13fd

CI note: I checked the remaining red Node 20 job. The invalid-argument coverage added in this PR passes in that run; the failure is in test/server/cloudflareWorkers.test.ts with a Miniflare network connection lost error, which is outside the touched server validation path. I also tried to rerun the failed job, but GitHub requires repo admin rights for that.

Rebased on current main, resolved the test conflicts after the experimental tasks removal, added the missing @modelcontextprotocol/server patch changeset, and force-pushed the branch.

Validated locally:

• pnpm changeset status --since origin/main (@modelcontextprotocol/server patch)
• pnpm --filter @modelcontextprotocol/server typecheck
• pnpm --filter @modelcontextprotocol/server lint
• pnpm --filter @modelcontextprotocol/test-integration lint
• pnpm --filter @modelcontextprotocol/test-integration test -- test/server/mcp.test.ts test/standardSchema.test.ts (144 passed)
• git diff --check origin/main..HEAD

The pre-push hook also completed the repo-wide build, typecheck, and lint steps successfully.

Rebased and force-pushed the branch.

I also updated the e2e contract expectations so invalid tool arguments now assert JSON-RPC -32602 instead of an isError tool result. Targeted validation passed:

• pnpm --filter @modelcontextprotocol/server exec vitest run test/server/mcp.compat.test.ts
• pnpm --filter @modelcontextprotocol/test-e2e test -- scenarios/tools.test.ts
• pnpm --filter @modelcontextprotocol/test-e2e test -- scenarios/standard-schema.test.ts
• pnpm --filter @modelcontextprotocol/test-e2e test -- scenarios/validation.test.ts
• pnpm --filter @modelcontextprotocol/server typecheck
• pnpm --filter @modelcontextprotocol/server lint
• pnpm --filter @modelcontextprotocol/server build
• pnpm --filter @modelcontextprotocol/test-e2e typecheck
• pnpm --filter @modelcontextprotocol/test-e2e lint
• git diff --check origin/main..HEAD

One combined e2e invocation hit a Vitest worker process exit after the relevant files had already run; rerunning the scenarios individually passed, so I split the validation above. The push hook also completed the repo-level build/typecheck/lint successfully.